home *** CD-ROM | disk | FTP | other *** search
- In article <jrb.21.0010B096@ag-eco.tamu.edu> jrb@ag-eco.tamu.edu (Jennifer Berry) writes:
-
- >Problem: Too few network buffers.
-
- >Question: Where do I find the settings for these netowrk buffers? Net.cfg?
- >System.ini? Trumpwsk.ini?
-
- This can happen if you don't have enough conventional (0-640k) memory free
- when tcpman executes. Try to free up some memory before windows loads, or
- make tcpman the first thing executed when windows starts up.
-
-
-
- jlewis@inorganic5.chem.ufl.edu
- if that bounces back, use
- jlewis@nervm.nerdc.ufl.edu
- From pbh@MIT.EDU Wed Mar 16 10:01:57 1994
- Received: from MIT.EDU (MIT.MIT.EDU) by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
- id AA07893; Wed, 16 Mar 1994 10:01:57 -0500
- Received: from ASHPOOL.MIT.EDU by MIT.EDU with SMTP
- id AA11964; Wed, 16 Mar 94 10:01:54 EST
- Message-Id: <9403161501.AA11964@MIT.EDU>
- To: Multiple recipients of list <winsock@sunsite.unc.edu>
- Subject: Re: SOCK_DGRAM support in WinSock
- Date: Wed, 16 Mar 94 10:01:51
- From: pbh@MIT.EDU
-
- >: Can any one tell me if SOCK_DGRAM protocol is supported by
- >: AND are there any WinSock suppliers that support SOCK_DGRAM?
- >
- >We have tested a few suppliers for this:
- >6) Novell LWP 4.12
- >
- >Didn't receive any, maybe we had a subnet mask problem or something?
-
- We have some applications developed here that use LWP and SOCK_DGRAM. We
- see no problems. This includes both the wlibsock API and the winsock API
- support.
-
-